home *** CD-ROM | disk | FTP | other *** search
ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) NNNNAAAAMMMMEEEE fstab - static information about filesystems DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN The file /_e_t_c/_f_s_t_a_b describes the filesystems and swapping partitions used by the local machine. The system administrator can modify it with a text editor. It is read by commands that mount, unmount, and check the consistency of filesystems. The file consists of a number of lines of the form: _f_i_l_e_s_y_s_t_e_m _d_i_r_e_c_t_o_r_y _t_y_p_e _o_p_t_i_o_n_s _f_r_e_q_u_e_n_c_y _p_a_s_s For example: /dev/root / xfs rw 0 0 Fields are separated by white space; a `#' as the first non-white space character indicates a comment. The entries from this file are accessed using the routines in _g_e_t_m_n_t_e_n_t(3), which return a structure of the following form: struct mntent { char *mnt_fsname; /* filesystem name */ char *mnt_dir; /* filesystem path prefix */ char *mnt_type; /* e.g. xfs, nfs, proc, or ignore */ char *mnt_opts; /* rw, ro, hard, soft, etc. */ int mnt_freq; /* dump frequency, in days */ int mnt_passno; /* parallel fsck pass number */ }; This structure is defined in the <_m_n_t_e_n_t._h> include file. To compile and link a program that calls _g_e_t_m_n_t_e_n_t(3), follow the procedures for section (3Y) routines as described in _i_n_t_r_o(3). The _m_n_t__d_i_r field is the full pathname of the directory to be mounted on. The _m_n_t__t_y_p_e field determines how the _m_n_t__f_s_n_a_m_e and _m_n_t__o_p_t_s fields are interpreted. Here is a list of the filesystem types currently supported, and the way each of them interprets these fields: xxxxffffssss _m_n_t__f_s_n_a_m_e must be a block special device (for example, /_d_e_v/_r_o_o_t) or a logical volume. eeeeffffssss _m_n_t__f_s_n_a_m_e must be a block special device (for example, /_d_e_v/_r_o_o_t) or a logical volume. pppprrrroooocccc _m_n_t__f_s_n_a_m_e should be the /_p_r_o_c directory. See _p_r_o_c(4). ffffdddd _m_n_t__f_s_n_a_m_e should be the /_d_e_v/_f_d directory. See _f_d(4). PPPPaaaaggggeeee 1111 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) hhhhwwwwggggffffssss _m_n_t__f_s_n_a_m_e should be the /_h_w directory. See _h_w_g_f_s(4). nnnnffffssss _m_n_t__f_s_n_a_m_e is the path on the server of the directory to be served. (NFS option only). ccccddddffffssss A synonym for type iiiissssoooo9999666666660000 (see below). This type is required for MIPS ABI compliance. iiiissssoooo9999666666660000 _m_n_t__f_s_n_a_m_e formerly was a generic SCSI device. With 6.2 plus patches, or later releases, it is the volume partition of the raw disk (for example, /_d_e_v/_r_d_s_k/_d_k_s_0_d_7_v_o_l). See _d_s(7M). This filesystem type is used to mount CD-ROM discs in ISO 9660 (with or without Rock Ridge extensions) and High Sierra formats. _e_o_e._s_w._c_d_r_o_m must be installed in order to use the iiiissssoooo9999666666660000 filesystem type. ddddoooossss _m_n_t__f_s_n_a_m_e is normally a floppy device, or other removable media using the disk driver. These are located in the directory /_d_e_v/_r_d_s_k (for example, /_d_e_v/_r_d_s_k/_f_d_s_0_d_2._3._5). See _d_k_s_c(7M) and _s_m_f_d(7M). hhhhffffssss _m_n_t__f_s_n_a_m_e must be either a floppy device or a raw disk device. Floppy devices are located in the directory /_d_e_v/_r_d_s_k (for example, /_d_e_v/_r_d_s_k/_f_d_s_0_d_2._3._5_h_i). See _s_m_f_d(7M). Raw disk devices are located in the directory /_d_e_v/_r_d_s_k (for example, /_d_e_v/_r_d_s_k/_d_k_s_0_d_4_v_o_l). See _d_s(7M). sssswwwwaaaapppp _m_n_t__f_s_n_a_m_e should be the full pathname to the file or block device to be used as a swap resource. ccccaaaacccchhhheeeeffffssss _m_n_t__f_s_n_a_m_e should be the filesystem name for the backing filesystem to be mounted as a cache filesystem. This will either be the special filename (for example, /_d_e_v/_d_s_k/_d_k_s_0_d_4_s_7) or _h_o_s_t:_p_a_t_h. rrrraaaawwwwddddaaaattttaaaa _m_n_t__f_s_n_a_m_e may be the block/char special device of the partition or logical volume to reserve (_m_n_t__d_i_r is ignored). This entry enables the system utilities (for example, _m_k_f_s, _m_o_u_n_t, and so on) to treat the raw partition or logical volume as 'mounted', preventing the partition from inadvertently being overwritten. Any packages that require dedicated raw partitions (databases and so on) should consider placing a rrrraaaawwwwddddaaaattttaaaa entry in _f_s_t_a_b(4). If the _m_n_t__t_y_p_e is specified as iiiiggggnnnnoooorrrreeee, then the entry is ignored. This is useful to show disk partitions not currently used. _m_n_t__f_r_e_q is not used in current IRIX systems. _m_n_t__p_a_s_s_n_o can be used to control the behavior of parallel filesystem checking on bootup, see _f_s_c_k(1M). PPPPaaaaggggeeee 2222 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) The _m_n_t__o_p_t_s field contains a list of comma-separated option words. Some _m_n_t__o_p_t_s are valid for all filesystem types, while others apply to a specific type only. Options valid on all filesystems (the default is rrrrwwww) are: rrrrwwww Read/write. rrrroooo Read-only. nnnnooooaaaauuuuttttoooo Ignore this entry during a _m_o_u_n_t ----aaaa command, to allow the definition of _f_s_t_a_b entries for commonly-used filesystems that should not be automatically mounted. ggggrrrrppppiiiidddd Causes a file created within the filesystem to have the group ID of its parent directory, not the creating process's group ID. nnnnoooossssuuuuiiiidddd Setuid execution not allowed for non-superusers. This option has no effect for the superuser. nnnnooooddddeeeevvvv Access to character and block special files is disallowed. Mandatory Access Control options can be specified using a list of colon- separated options: eeeeaaaagggg:_o_p_t_i_o_n{:_o_p_t_i_o_n ...} where _o_p_t_i_o_n is one of the following: mmmmaaaacccc----ddddeeeeffffaaaauuuulllltttt=_l_a_b_e_l Use the specified label for all files on the specified file system that do not have a MAC label. mmmmaaaacccc----iiiipppp=_l_a_b_e_l Use the specified label for communications to other systems regarding this file system. A number of filesystem types also support the ddddeeeebbbbuuuugggg option, but the meaning varies with the filesystem type. Options specific only to xxxxffffssss,,,, eeeeffffssss and nnnnffffssss filesystems are: qqqquuuuoooottttaaaa Disk quota accounting enabled, and limits enforced. Options specific to xxxxffffssss filesystems are: bbbbiiiioooossssiiiizzzzeeee The biosize (buffered I/O size) option can be used to set the default preferred buffered I/O size for filesystem. The default preferred I/O size is 64K. The biosize option can be used to decrease the preferred I/O size. The size must be expressed as the log (base2) of the desired I/O size. Valid PPPPaaaaggggeeee 3333 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) values for this option are 14 through 16, inclusive (e.g. 16K, 32K, and 64K bytes). On machines with 4K size pages, 13 (8 Kbytes) is also a valid size. The preferred buffered I/O size can also be altered on a per-file basis using the _f_c_n_t_l system call. See _f_c_n_t_l(2) for further details. ddddmmmmiiii Enable the Data Management Interface event callouts. llllooooggggbbbbuuuuffffssss Set the number of in memory log buffers. Valid numbers range from 2-8 inclusive. The default value is 8 buffers for filesystems with a blocksize of 64K, 4 buffers for filesystems with a blocksize of 32K, 3 buffers for filesystems with a blocksize of 16K, and 2 buffers for all other configurations. Increasing the number of buffers may increase performance on some workloads at the cost of the memory used for the extra log buffers and their associated control structures. nnnnooooaaaalllliiiiggggnnnn Data allocations will not be aligned at stripe unit boundaries. nnnnooooaaaattttiiiimmmmeeee Access timestamps are not updated when a file is read. nnnnoooorrrreeeeccccoooovvvveeeerrrryyyy The filesystem will be mounted without running log recovery. If the filesystem was not cleanly unmounted, it is likely to be inconsistent when mounted in norecovery mode. Some files or directories may not be accessible because of this. Filesystems mounted norecovery must be mounted read-only or the mount will fail. oooossssyyyynnnncccciiiissssddddssssyyyynnnncccc Make writes to files opened with the O_SYNC flag set behave as if the O_DSYNC flag had been used instead. This can result in better performance without compromising data safety. However if this option in effect, timestamp updates from O_SYNC writes can be lost if the system crashes. qqqqnnnnooooeeeennnnffffoooorrrrcccceeee Disk quota accounting enabled, but limits are not enforced. ppppqqqquuuuoooottttaaaa Project disk quota accounting enabled and limits enforced. ppppqqqqnnnnooooeeeennnnffffoooorrrrcccceeee Project disk quota accounting enabled, but limits are not enforced. ssssuuuunnnniiiitttt=_v_a_l_u_e Used to specify the stripe unit for a RAID device or a xlv stripe volume. _v_a_l_u_e has to be specified in 512-byte block units. If this option is not specified and the filesystem was made on a stripe volume or the stripe unit was specified for the RAID device at mkfs time, then the mount system call will restore the value from the superblock. For filesystems that are PPPPaaaaggggeeee 4444 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) made directly on RAID devices, this option can be used to override the information in the superblock if the underlying disk layout changes after the filesystem has been mkfsed. If the filesystem is made on a xlv volume, then this will be done implicitly. sssswwwwiiiiddddtttthhhh=_v_a_l_u_e Used to specify the stripe width for a RAID device or a xlv stripe volume. _v_a_l_u_e has to be specified in 512-byte block units. If this option is not specified, and the filesystem was made on a stripe volume or the stripe width was specified for the RAID device at mkfs time, then the mount system call will restore the value from the superblock. For filesystems that are made directly on RAID devices, this option can be used to override the information in the superblock if the underlying disk layout changes after the filesystem has been mkfsed. If the filesystem is made on a xlv volume, then this will be done implicitly. This option is required if the ----oooo ssssuuuunnnniiiitttt option has been specified. Also it has to be a multiple of the sunit option. wwwwssssyyyynnnncccc All operations that modify the filesystem are synchronous except for writes to user files (e.g. create, unlink, mv, truncate, etc.). This option can be used in conjunction with exporting a filesystem -wsync to obtain NFS write-synchronous semantics, if so desired. See eeeexxxxppppoooorrrrttttssss((((4444)))) for further information. Options specific to eeeeffffssss filesystems (the default is ffffsssscccckkkk, nnnnooooqqqquuuuoooottttaaaa) are: rrrraaaawwww=_p_a_t_h The filesystem's raw device pathname (for example, /_d_e_v/_r_r_o_o_t). ffffsssscccckkkk _f_s_c_k(1M) invoked with no filesystem arguments should check this filesystem. nnnnooooffffsssscccckkkk _f_s_c_k(1M) should not check this filesystem by default. nnnnooooqqqquuuuoooottttaaaa Disk quota accounting and limit enforcement disabled. llllbbbbssssiiiizzzzeeee=_n The number of bytes transferred in each read or synchronous write operation. The value assigned to the llllbbbbssssiiiizzzzeeee option must be a power of two at least as large as the system page size. This value is returned by the _g_e_t_p_a_g_e_s_i_z_e(2) system call and is normally either 4096 or 16384 depending on the system type. The current default for llllbbbbssssiiiizzzzeeee is the value in the fs_sectors field of the superblock of the filesystem. This was normally the number of "sectors per track" in the past, but that often fictitious value is no longer used. If not set on the mkfs command line, the maximum value of 128 sectors is used by IRIX 6.4 and later releases. An invalid size will cause the mount to fail with PPPPaaaaggggeeee 5555 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) the error EINVAL. The maximum size is currently 65536. Note that less than llllbbbbssssiiiizzzzeeee bytes will be transferred if there are not llllbbbbssssiiiizzzzeeee contiguous bytes of the addressed portion of the file on disk. Options specific to ddddoooossss filesystems. ppppaaaarrrrttttiiiittttiiiioooonnnn With a following number, as ppppaaaarrrrttttiiiittttiiiioooonnnn,,,,####, where #### is most often either 1 or 4, is used with type 5 (extended) filesystems to specify which partition to use. Otherwise type 5 filesystems are not supported. Options specific to iiiissssoooo9999666666660000 filesystems (the default is rrrrwwww, which has no effect since CD-ROM discs are always read-only) are: sssseeeettttxxxx Set execute permission on every file on the mounted filesystem. The default is to make an intelligent guess based on the first few bytes of the file. nnnnoooottttrrrraaaannnnssssllllaaaatttteeee Don't translate ISO 9660 filenames to UNIX filenames. The default is to convert upper case to lower case and to truncate the part including and after the semicolon. ccccaaaacccchhhheeee=_b_l_o_c_k_s Set the number of 2048 byte blocks to be used for caching directory contents. The default is to cache 128 blocks. nnnnooooeeeexxxxtttt Ignore Rock Ridge extensions. The default when the nnnnooooeeeexxxxtttt option is not specified is to use Rock Ridge extensions if present. ssssuuuusssspppp Enable processing of System Use Sharing Protocol extensions to the ISO 9660 specification. This is the default. nnnnoooossssuuuusssspppp Disable processing of System Use Sharing Protocol extensions. This has the same effect as the nnnnooooeeeexxxxtttt option. rrrrrrrriiiipppp Enable processing of the Rock Ridge extensions. This is the default. nnnnoooorrrrrrrriiiipppp Disable processing of the Rock Ridge extensions. This is equivalent to the nnnnooooeeeexxxxtttt option. nnnnmmmmccccoooonnnnvvvv====[[[[ccccllllmmmm]]]] This option is supplied for MIPS ABI compliance; some non-IRIX systems may implement it only for type ccccddddffffssss, IRIX allows it with type iiiissssoooo9999666666660000 also. Only one of the three letters cccc, llll, or mmmm can be specified. This option controls filename translation. cccc has the same meaning as nnnnoooottttrrrraaaannnnssssllllaaaatttteeee above. llll requests translation to lower case (the IRIX default), and mmmm suppresses PPPPaaaaggggeeee 6666 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) the version number (also the IRIX default). NFS clients can mount iiiissssoooo9999666666660000, ddddoooossss, and hhhhffffssss filesystems remotely by specifying _h_o_s_t_n_a_m_e:_m_o_u_n_t_p_o_i_n_t for _f_i_l_e_s_y_s_t_e_m and nnnnffffssss for _t_y_p_e, where an iiiissssoooo9999666666660000, ddddoooossss, or hhhhffffssss filesystem is mounted at _m_o_u_n_t_p_o_i_n_t on the host _h_o_s_t_n_a_m_e. In this case, the same _o_p_t_i_o_n_s apply as with nnnnffffssss (see below). If the NFS option is installed, the following options are valid for nnnnffffssss filesystems: vvvveeeerrrrssss====_n Use NFS protocol version _n. (The default is to try version 3, falling back to version 2 if the version 3 mount fails.) bbbbgggg If the first attempt fails, retry in the background. ffffgggg Retry in foreground. (Default) rrrreeeettttrrrryyyy====_n Set number of mount failure retries to _n. (Default = 10000) rrrrssssiiiizzzzeeee====_n Set read transfer size to _n bytes. This value will be rounded up to the nearest multiple of 512 bytes. The default is 8192 for NFS version 2, and 16384 or 32768 for NFS version 3. The 16KB transfer size is used when the route to the server is known to go through a router, or when the Maximum Transmission Unit (MTU) of the interface used to get to the server is Ethernet-sized (about 1500 bytes) or less. The system tunable nnnnffffssss3333____ddddeeeeffffaaaauuuulllltttt____xxxxffffeeeerrrr can be used to reduce the upper limit of the NFS version 3 transfer size if 16KB is still too much for routers. For example, setting it to 8192 gives the same default for version 3 as version 2. For NFS version 3, the read transfer size specified by the server will be used if it is smaller than either the default or what the user has specified. wwwwssssiiiizzzzeeee====_n Set write transfer size to _n bytes. This value will be rounded up to the nearest multiple of 512 bytes. The default is the same as for the read size. For NFS version 3, the write transfer size specified by the server will be used if it is smaller than either the default or what the user has specified. ttttiiiimmmmeeeeoooo====_n Set NFS timeout to _n tenths of a second. (Default = 11) rrrreeeettttrrrraaaannnnssss====_n Set number of NFS retransmissions to _n. (Default = 5) ppppoooorrrrtttt====_n Set server UDP port number to _n. (Default = 2049) hhhhaaaarrrrdddd Retry request until server responds. (Default) ssssoooofffftttt Return error if server doesn't respond. PPPPaaaaggggeeee 7777 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) nnnnooooiiiinnnnttttrrrr Disallow requests to be interrupted by the following signals: SIGHUP, SIGINT, SIGQUIT, SIGKILL, SIGTERM, and SIGTSTP. (Requests are interruptible by these signals, by default.) aaaaccccrrrreeeeggggmmmmiiiinnnn=_t Set the regular file minimum attribute cache timeout to _t seconds. (Default = 3) aaaaccccrrrreeeeggggmmmmaaaaxxxx=_t Set the regular file maximum attribute cache timeout to _t seconds. (Default = 60) aaaaccccddddiiiirrrrmmmmiiiinnnn=_t Set the directory minimum attribute cache timeout to _t seconds. (Default = 30) aaaaccccddddiiiirrrrmmmmaaaaxxxx=_t Set the directory maximum attribute cache timeout to _t seconds. (Default = 60) aaaaccccttttiiiimmmmeeeeoooo=_t Set regular and directory minimum and maximum attribute cache timeouts to _t seconds. nnnnooooaaaacccc No attribute caching. pppprrrroooottttoooo=_x_y_z Use the IP protocol _x_y_z , where _x_y_z is either _u_d_p or _t_c_p . If the specified protocol is not supported by the server, then the mount will fail. The default is _u_d_p . pppprrrriiiivvvvaaaatttteeee Do not flush delayed writes on last close of an open file, and use local file and record locking instead of a remote lock manager. sssshhhhoooorrrrttttuuuuiiiidddd Do not let users with userids or groupids larger than 65535 (see _i_d(1M)) create or own files. Some versions of UNIX do not support large userids; trying to create a file with a large userid on such an NFS server can produce undefined and surprising results. ssssyyyymmmmttttttttllll=_t Set the time-to-live for symbolic links cached by NFS to _t seconds. ssssyyyymmmmttttttttllll====0000 turns off NFS symlink caching. The maximum value for _t is 3600. (Default = 3600) aaaassssyyyynnnnccccnnnnllllmmmm Use asynchronous NLM RPC calls. The default is to use synchronous NLM. Using this option requires that _l_o_c_k_d(1M) be running. ddddeeeeffffxxxxaaaattttttttrrrr Use default values for system-defined extended attributes, rather than asking the NFS server for their values. This option does not work when nnnnooooaaaacccc is also specified. PPPPaaaaggggeeee 8888 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) nnnnooooddddeeeeffffxxxxaaaattttttttrrrr Always ask the server for extended attributes (required for Trusted Irix). ddddooooxxxxaaaattttttttrrrr Tell the NFS server that this client can be trusted to properly handle extended attributes. This is necessary only when the remote filesystem is exported with the nnnnooooxxxxaaaattttttttrrrr option. The bbbbgggg option causes _m_o_u_n_t to run in the background if the server's _m_o_u_n_t_d(1M) does not respond. _m_o_u_n_t attempts each request rrrreeeettttrrrryyyy====_n times before giving up. Once the filesystem is mounted, each NFS request waits ttttiiiimmmmeeeeoooo====_n tenths of a second for a response. If no response arrives, the time-out is multiplied by 2, up to a maximum of MAXTIMO (900), and the request is retransmitted. When rrrreeeettttrrrraaaannnnssss====_n retransmissions have been sent with no reply a ssssoooofffftttt mounted filesystem returns an error on the request and a hhhhaaaarrrrdddd mounted filesystem retries the request. Filesystems that are mounted rrrrwwww (read-write) should use the hhhhaaaarrrrdddd option. The number of bytes in a read or write request can be set with the rrrrssssiiiizzzzeeee and wwwwssssiiiizzzzeeee options. In the absence of client activity that would invalidate recently acquired file attributes, NFS holds attributes cached for an interval between aaaaccccrrrreeeeggggmmmmiiiinnnn and aaaaccccrrrreeeeggggmmmmaaaaxxxx for regular files, and between aaaaccccddddiiiirrrrmmmmiiiinnnn and aaaaccccddddiiiirrrrmmmmaaaaxxxx for directories. The aaaaccccttttiiiimmmmeeeeoooo option sets all attribute timeout constraints to a given number of seconds. The nnnnooooaaaacccc option disables attribute caching altogether. The pppprrrriiiivvvvaaaatttteeee option greatly improves write performance by caching data and delaying writes on the assumption that only this client modifies files in the remote filesystem. It should be used only if the greater risk of lost delayed-write data in the event of a crash is acceptable given better performance. EFS uses caching strategies similar to private NFS The system reduces the risk of data loss for all filesystems by automatically executing a partial _s_y_n_c(2) at regular intervals. If the BDS option is installed, the following options are valid for nnnnffffssss filesystems that have BDS service enabled: bbbbddddssss Turn on bulk data service for this file system. bbbbddddssssaaaauuuuttttoooo=_s_i_z_e For all read/write requests that are sized greater or equal to _s_i_z_e, do BDS I/O instead of NFS I/O. bbbbddddsssswwwwiiiinnnnddddoooowwww=_s_i_z_e Set the TCP protocol send and receive windows to _s_i_z_e instead of the default of 4Mbytes. bbbbddddssssbbbbuuuuffffffffeeeerrrr=_s_i_z_e Specify the size of data buffers within the server, instead of allowing the server to determine the best size. PPPPaaaaggggeeee 9999 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) bbbbddddsssspppprrrroooottttoooo=[_s_t_p|_t_c_p] Specify the transmission protocol to use. stp is the Scheduled Transfer Protocol. tcp is the Transmission Control Protocol. The ssssttttpppp option is available only on the Origin and the Octane platforms currently. Not specifying this option at all will cause BDS by default to use the tcp transmission protocol. bbbbddddssssvvvvccccccccoooonnnnttttrrrroooollll=_c_i_r_c_u_i_t_N_u_m_b_e_r Specify the virtual circuit to use, over the ST protocol, for BDS command packets. This option is only applicable to BDS over ST protocol (see bdsproto above). See also ST_OUT_VCNUM in the STP(7P) man page for more information. Options specific to sssswwwwaaaapppp resources are: pppprrrriiii=_t Set the priority of the swap device to _t. The legal values are from 0 to 7 inclusive. sssswwwwpppplllloooo=_t Set the first 512 byte block to use to _t (default is 0). lllleeeennnnggggtttthhhh=_t Set the number of 512 byte blocks to use to _t (default is entire file/partition). mmmmaaaaxxxxlllleeeennnnggggtttthhhh=_t Set the maximum number of 512 byte blocks to grow the swap area to _t (default is to use lllleeeennnnggggtttthhhh). vvvvlllleeeennnnggggtttthhhh=_t Set the number of virtual 512 byte blocks to claim this swap file has to _t (default is to use lllleeeennnnggggtttthhhh). All other options except for _n_o_a_u_t_o are ignored for _ssss_wwww_aaaa_pppp files. If the CacheFS option is installed, the following options are valid for ccccaaaacccchhhheeeeffffssss filesystems: bbbbaaaacccckkkkffffssssttttyyyyppppeeee=_f_i_l_e__s_y_s_t_e_m__t_y_p_e The filesystem type of the back filesystem (for example, nnnnffffssss). Any of the following filesystem types may be used as the back filesystem: _n_f_s, _n_f_s_3, _i_s_o_9_6_6_0, _d_o_s, _c_d_f_s, _k_f_s, or _h_f_s. If this option is not specified, the back filesystem type is determined from the filesystem name. Filesystem names of the form _h_o_s_t_n_a_m_e:_p_a_t_h will be assumed to be type _n_f_s. bbbbaaaacccckkkkppppaaaatttthhhh=_p_a_t_h Specifies where the back filesystem is already mounted. If this argument is not supplied, CacheFS determines a mount point for the back filesystem. ccccaaaacccchhhheeeeddddiiiirrrr=_d_i_r_e_c_t_o_r_y The name of the cache directory. PPPPaaaaggggeeee 11110000 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) ccccaaaacccchhhheeeeiiiidddd=_I_D _I_D is a string specifying a particular instance of a cache. If you do not specify a cache ID, CacheFS will construct one. wwwwrrrriiiitttteeee----aaaarrrroooouuuunnnndddd | nnnnoooonnnn----sssshhhhaaaarrrreeeedddd Write modes for CacheFS. In the wwwwrrrriiiitttteeee----aaaarrrroooouuuunnnndddd mode, writes are made to the back filesystem, and the affected file is purged from the cache. Also in this mode, file and record locking is performed through the back filesystem. You can use the nnnnoooonnnn---- sssshhhhaaaarrrreeeedddd mode (the default) when you are sure that no one else will be writing to the cached filesystem. In this mode, all writes are made to both the front and the back filesystem, and the file remains in the cache. nnnnooooccccoooonnnnsssstttt By default, consistency checking is performed. Disable consistency checking by specifying nnnnooooccccoooonnnnsssstttt only if you mount the filesystem read-only. pppprrrriiiivvvvaaaatttteeee Causes file and record locking to be performed locally. In addition, files remain cached when file and record locking is performed. By default, files are not cached when file and record locking is performed and all file and record locking is handled by the back filesystem. llllooooccccaaaallll----aaaacccccccceeeessssssss Causes the front filesystem to interpret the mode bits used for access checking instead or having the back filesystem verify access permissions. ssssuuuuiiiidddd | nnnnoooossssuuuuiiiidddd Allow (default) or disallow set-uid execution. aaaaccccrrrreeeeggggmmmmiiiinnnn=_n Specifies that cached attributes are held for at least _n seconds after file modification. After _n seconds, CacheFS checks to see if the file modification time on the back filesystem has changed. If it has, all information about the file is purged from the cache and new data is retrieved from the back filesystem. The default value is 30 seconds. aaaaccccrrrreeeeggggmmmmaaaaxxxx=_n Specifies that cached attributes are held for no more than _n seconds after file modification. After _n seconds, all file information is purged from the cache. The default value is 30 seconds. aaaaccccddddiiiirrrrmmmmiiiinnnn=_n Specifies that cached attributes are held for at least _n seconds after directory update. After _n seconds, CacheFS checks to see if the directory modification time on the back filesystem has changed. If it has, all information about the directory is purged from the cache and new data is retrieved PPPPaaaaggggeeee 11111111 ffffssssttttaaaabbbb((((4444)))) ffffssssttttaaaabbbb((((4444)))) from the back filesystem. The default value is 30 seconds. aaaaccccddddiiiirrrrmmmmaaaaxxxx=_n Specifies that cached attributes are held for no more than _n seconds after directory update. After _n seconds, all directory information is purged from the cache. The default value is 30 seconds. aaaaccccttttiiiimmmmeeeeoooo=_n Sets aaaaccccrrrreeeeggggmmmmiiiinnnn, aaaaccccrrrreeeeggggmmmmaaaaxxxx, aaaaccccddddiiiirrrrmmmmiiiinnnn, and aaaaccccddddiiiirrrrmmmmaaaaxxxx to _n. bbbbgggg This option causes _m_o_u_n_t to run in the background if the back filesystem mount times out. ddddiiiissssccccoooonnnnnnnneeeecccctttt Causes the cache filesystem to operate in disconnected mode when the back filesystem fails to respond. This causes read accesses to files already cached to be fulfilled from the front filesystem even when the back filesystem does not respond. NNNNOOOOTTTTEEEESSSS The filesystem types nnnnffffssss2222, nnnnffffssss3333, and nnnnffffssss3333pppprrrreeeeffff are accepted for compatibility with earlier releases. nnnnffffssss2222 is equivalent to vvvveeeerrrrssss====2222. nnnnffffssss3333 is equivalent to vvvveeeerrrrssss====3333. nnnnffffssss3333pppprrrreeeeffff is equivalent to nnnnffffssss with no vvvveeeerrrrssss==== option. Options used by the _m_o_u_n_t(1M) command on normal filesystems are ignored when applied to the root filesystem, since the _f_s_t_a_b file cannot be read before mounting the root filesystem. These options include rrrrwwww and rrrroooo (the root filesystem cannot be mounted read-only), ggggrrrrppppiiiidddd, qqqquuuuoooottttaaaa and qqqqnnnnooooeeeennnnffffoooorrrrcccceeee (see _q_u_o_t_a_o_n(1M), ddddmmmmiiii, wwwwssssyyyynnnncccc, nnnnooooaaaattttiiiimmmmeeee, nnnnooooaaaalllliiiiggggnnnn, ssssuuuunnnniiiitttt, sssswwwwiiiiddddtttthhhh, nnnnooooqqqquuuuoooottttaaaa, and llllbbbbssssiiiizzzzeeee.... FFFFIIIILLLLEEEESSSS /etc/fstab SSSSEEEEEEEE AAAALLLLSSSSOOOO cfsadmin(1M), fsck(1M), mount(1M), quotacheck(1M), quotaon(1M), swap(1M), getmntent(3), efs(4), exports(4), fd(4), filesystems(4), mtab(4), proc(4), xfs(4). PPPPaaaaggggeeee 11112222 
